From: Wei Liu Date: Wed, 1 Aug 2018 09:03:07 +0000 (+0100) Subject: xen: clean up altp2m op comment X-Git-Tag: archive/raspbian/4.14.0+80-gd101b417b7-1+rpi1^2~63^2~3522 X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=98b92f26019bab403d3e5fa74dbec4bf8a541de4;p=xen.git xen: clean up altp2m op comment Delete trailing spaces and refer to XSM instead of an internal function in the public header. Signed-off-by: Wei Liu Reviewed-by: George Dunlap Acked-by: Jan Beulich --- diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c index 5de544093e..72c51faecb 100644 --- a/xen/arch/x86/hvm/hvm.c +++ b/xen/arch/x86/hvm/hvm.c @@ -4468,16 +4468,16 @@ static int hvmop_get_param( } /* - * altp2m operations are envisioned as being used in several different + * altp2m operations are envisioned as being used in several different * modes: - * + * * - external: All control and decisions are made by an external agent * running domain 0. * * - internal: altp2m operations are used exclusively by an in-guest * agent to protect itself from the guest kernel and in-guest * attackers. - * + * * - coordinated: An in-guest agent handles #VE and VMFUNCs locally, * but makes requests of an agent running outside the domain for * bigger changes (such as modifying altp2m entires). @@ -4491,7 +4491,7 @@ static int hvmop_get_param( * to properly enable the 'internal' use case, as well as to avoid * fragmentation, all altp2m subops should come under this single * HVMOP. - * + * * Note that 'internal' mode (HVM_PARAM_ALTP2M == XEN_ALTP2M_mixed) * has not been evaluated for safety from a security perspective. * Before using this mode in a security-critical environment, each diff --git a/xen/include/public/hvm/params.h b/xen/include/public/hvm/params.h index daa28a86be..396977c2bb 100644 --- a/xen/include/public/hvm/params.h +++ b/xen/include/public/hvm/params.h @@ -243,7 +243,7 @@ * Note that 'mixed' mode has not been evaluated for safety from a * security perspective. Before using this mode in a * security-critical environment, each subop should be evaluated for - * safety, with unsafe subops blacklisted in xsm_hvm_altp2mhvm_op(). + * safety, with unsafe subops blacklisted in XSM. */ #define HVM_PARAM_ALTP2M 35 #define XEN_ALTP2M_disabled 0